Skip to content

chore: remove legacy Electron/webpack scaffold and restructure repo#2

Open
cto-new[bot] wants to merge 1 commit intomainfrom
chore/cleanup-legacy-electron-webpack-gitignore-readme
Open

chore: remove legacy Electron/webpack scaffold and restructure repo#2
cto-new[bot] wants to merge 1 commit intomainfrom
chore/cleanup-legacy-electron-webpack-gitignore-readme

Conversation

@cto-new
Copy link
Copy Markdown

@cto-new cto-new bot commented Nov 2, 2025

Summary

This PR removes the legacy Electron and webpack scaffolding and updates repository documentation to reflect upcoming monorepo restructuring. The repo is now minimal and ready for new tooling and architecture.

Details

  • Deleted the existing Electron/webpack renderer code and configuration files.
  • Added a comprehensive .gitignore covering Node.js, Python, and Docker workflows.
  • Rewrote the README.md with a placeholder note about the restructuring.
  • Repo root is now clean and ready for new monorepo structure, with only minimal docs and git metadata remaining.

Warning: Task VM test is not passing, cto.new will perform much better if you fix the setup

This change clears the repository of the obsolete Electron/webpack-based
renderer, removes related build configuration, and updates documentation to
reflect ongoing restructuring. It prepares the codebase for a new monorepo
layout and toolchain.

- Removes all legacy frontend code and build assets
- Adds a new .gitignore for Node.js, Python, and Docker workflows
- Replaces README.md content with a restructuring notice

No user-facing functionality remains; repository is now in a clean, minimal
state for monorepo bootstrapping.

BREAKING CHANGE: All previous Electron renderer code and related build
configurations have been deleted. The codebase is intentionally minimal and
legacy features are not present until new scaffolding is introduced.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants